home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: seebs@solutions.solon.com (Peter Seebach)
- Newsgroups: comp.lang.c++,comp.lang.c,comp.object,comp.software-eng
- Subject: Re: Portability of code & skills (Beware of "C" Hackers etc)
- Date: 29 Mar 1996 19:21:08 -0600
- Organization: Usenet Fact Police (Undercover)
- Message-ID: <4ji2a4$6rk@solutions.solon.com>
- References: <4ikb6kINN1is@mayne.ugrad.cs.ubc.ca> <4j6c48$4mr@bughouse.imonics.com> <315B0A17.489A@ix.netcom.com> <4jh25b$8s3@bughouse.imonics.com>
- NNTP-Posting-Host: solutions.solon.com
-
- In article <4jh25b$8s3@bughouse.imonics.com>,
- Imonics Corporation <rcook@imonics.com> wrote:
- >Unix has (and had) the alias mechanism for dealing with shortening commands.
- >If they had called the command something like "list", and you wanted to call
- >it "ls", and I wanted to call it "l", and she wanted to call it "dr", we
- >can (and could) all do that. And when one of us wanted to look up the
- >command using "man" (or "help"), it would have been much easier to remember
- >to look for "list" than for "ls".
-
- man -k list, or apropos list, does in fact point you to ls, under
- "list directory contents". apropos dir even points you to ls.
-
- >I don't think length is the reason for the cryptic names. "grep" could have
- >been called "find" without adding characters.
-
- But why? "find" was an existing command to find things. "grep" does not
- find things, it globally prints regular expressions. Since it was
- written after ed, everyone had been using g/re/p for ages, and it was
- an intuitive device.
-
- >"pwd" could have been called "pd"
- >if they had wanted just shorter commands (and, incidentally, to be consistent
- >with "cd" -- it should have been either "cwd"/"pwd" or "cd"/"pd"). Besides,
- >since alias is there, who are they to pick my abbreviations for me?
-
- alias wasn't there back then. :)
-
- >Or, if they DID do it for this reason, then it's a very poor reason. Glass
- >teletypes weren't that uncommon in the mid-70s, reasonable foresight would
- >have led to the conclusion that understanding the commands was more important
- >than typing them quickly in their raw (un-aliased) form.
-
- True. But you don't *understand* words. You remember them. "you" is not
- something that I remember because it's mnemonic, it's something I remember
- because it's short. "person I'm talking to" is too damn long.
-
- >But only if you wanted people to understand them easily.
-
- Understand easily, or use easily once you understand? :)
-
- Even today, with Unix's short lines, I frequently type 100+ character
- lines of commands.
-
- Should I type 200+ characters? No.
-
- -s
- --
- Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
- C/Unix wizard -- C/Unix questions? Send mail for help. No, really!
- FUCK the communications decency act. Goddamned government. [literally.]
- The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html
-